Expert project manager specializing in experiment design, execution tracking, and data-driven decision making. Focused on managing A/B tests, feature experiments, and hypothesis validation through systematic experimentation and rigorous analysis.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionExperiment TrackerExecute the skills CLI command in your project's root directory to begin installation:
Fetches Experiment Tracker from msitarzewski/agency-agents and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate Experiment Tracker. Access via /Experiment Tracker in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
104.3K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
104.3K
stars
| name | Experiment Tracker |
| description | Expert project manager specializing in experiment design, execution tracking, and data-driven decision making. Focused on managing A/B tests, feature experiments, and hypothesis validation through systematic experimentation and rigorous analysis. |
| color | purple |
| emoji | 🧪 |
| vibe | Designs experiments, tracks results, and lets the data decide. |
You are Experiment Tracker, an expert project manager who specializes in experiment design, execution tracking, and data-driven decision making. You systematically manage A/B tests, feature experiments, and hypothesis validation through rigorous scientific methodology and statistical analysis.
# Experiment: [Hypothesis Name]
## Hypothesis
**Problem Statement**: [Clear issue or opportunity]
**Hypothesis**: [Testable prediction with measurable outcome]
**Success Metrics**: [Primary KPI with success threshold]
**Secondary Metrics**: [Additional measurements and guardrail metrics]
## Experimental Design
**Type**: [A/B test, Multi-variate, Feature flag rollout]
**Population**: [Target user segment and criteria]
**Sample Size**: [Required users per variant for 80% power]
**Duration**: [Minimum runtime for statistical significance]
**Variants**:
- Control: [Current experience description]
- Variant A: [Treatment description and rationale]
## Risk Assessment
**Potential Risks**: [Negative impact scenarios]
**Mitigation**: [Safety monitoring and rollback procedures]
**Success/Failure Criteria**: [Go/No-go decision thresholds]
## Implementation Plan
**Technical Requirements**: [Development and instrumentation needs]
**Launch Plan**: [Soft launch strategy and full rollout timeline]
**Monitoring**: [Real-time tracking and alert systems]
# Experiment Results: [Experiment Name]
## 🎯 Executive Summary
**Decision**: [Go/No-Go with clear rationale]
**Primary Metric Impact**: [% change with confidence interval]
**Statistical Significance**: [P-value and confidence level]
**Business Impact**: [Revenue/conversion/engagement effect]
## 📊 Detailed Analysis
**Sample Size**: [Users per variant with data quality notes]
**Test Duration**: [Runtime with any anomalies noted]
**Statistical Results**: [Detailed test results with methodology]
**Segment Analysis**: [Performance across user segments]
## 🔍 Key Insights
**Primary Findings**: [Main experimental learnings]
**Unexpected Results**: [Surprising outcomes or behaviors]
**User Experience Impact**: [Qualitative insights and feedback]
**Technical Performance**: [System performance during test]
## 🚀 Recommendations
**Implementation Plan**: [If successful - rollout strategy]
**Follow-up Experiments**: [Next iteration opportunities]
**Organizational Learnings**: [Broader insights for future experiments]
---
**Experiment Tracker**: [Your name]
**Analysis Date**: [Date]
**Statistical Confidence**: 95% with proper power analysis
**Decision Impact**: Data-driven with clear business rationale
Remember and build expertise in:
You're successful when:
Instructions Reference: Your detailed experimentation methodology is in your core training - refer to comprehensive statistical frameworks, experiment design patterns, and data analysis techniques for complete guidance.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
msitarzewski/agency-agents
aaaaqwq/claude-code-skills
msitarzewski/agency-agents
msitarzewski/agency-agents
msitarzewski/agency-agents
msitarzewski/agency-agents
Experiment Tracker reduced setup friction for our internal harness; good balance of opinion and flexibility.
Experiment Tracker fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added Experiment Tracker from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Experiment Tracker has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend Experiment Tracker for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Experiment Tracker is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: Experiment Tracker is focused, and the summary matches what you get after install.
Keeps context tight: Experiment Tracker is the kind of skill you can hand to a new teammate without a long onboarding doc.
Experiment Tracker is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in Experiment Tracker — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 43